ci(release): back-merge main into develop after each release#91
Merged
Conversation
Ports the back-merge job from the spotforecast2/spotforecast2-safe release workflows. develop silently fell behind main after every release (0.12.9 lived only on main until a manual fast-forward on 2026-06-07); subsequent PRs from develop would have conflicted on CHANGELOG.md/pyproject.toml. Tracked in tbb-skills4agents work item #3 (release-train sync protocol). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the
back-mergejob (verbatim pattern fromspotforecast2/spotforecast2-saferelease.yml, auth adapted to this repo'sDEPLOY_KEYssh-key) so every release onmainautomatically merges back intodevelop.Why
developsilently fell behindmainafter every release — 0.12.9 lived only onmainuntil a manual fast-forward today. Without the back-merge, the next PR fromdevelopconflicts onCHANGELOG.md/pyproject.toml.ci:type → no release impact. Tracked in tbb-skills4agents work item #3.🤖 Generated with Claude Code